-
Notifications
You must be signed in to change notification settings - Fork 38.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix waiting for CRD sync at server start #118104
Conversation
verified this resolves the issue by starting a server and looking at logs, but need to figure out how to exercise this with a test |
added an integration test and ensured it failed on master without the startup fix |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/approve
LGTM label has been added. Git tree hash: fadf2eccff5811a82929c57efea739e351b35c5c
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: liggitt, logicalhan The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
forgot to close the etcd client I created in the integration test, which tripped the goroutine check:
pushed fix |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
LGTM label has been added. Git tree hash: d7d1c096466330b99a68042e5e6c8028f5e3aa8d
|
/triage accepted |
…104-upstream-release-1.26 Automated cherry pick of #118104: Fix waiting for CRD sync at server start
…104-upstream-release-1.25 Automated cherry pick of #118104: Fix waiting for CRD sync at server start
…104-upstream-release-1.24 Automated cherry pick of #118104: Fix waiting for CRD sync at server start
…104-upstream-release-1.27 Automated cherry pick of #118104: Fix waiting for CRD sync at server start
What type of PR is this?
/kind bug
/priority critical-urgent
What this PR does / why we need it:
Fixes logic checking whether we should wait for CRD sync at server start before reconciling APIService objects
Which issue(s) this PR fixes:
Fixes #118103
Test commit best reviewed ignoring whitespace (https://github.com/kubernetes/kubernetes/pull/118104/files?w=1)
Does this PR introduce a user-facing change?
/assign @deads2k
/sig api-machinery